================================================================================
                        ACADEMIC PLANNER PROJECT
                    COMPILED DAILY SCRUM SUBMISSIONS
                            Spring 2026

Team Members:
- Aaron Delarosa
- Faisal Alhazzaa  
- Ashley Paul
================================================================================

PROJECT OVERVIEW
================================================================================

Project Name: Academic Planner - AI-Powered Workload Management System
Team Size: 3 members
Project Duration: 8 weeks (with project pivot)
Total Scrum Meetings: 4 documented sessions

Note: Team switched project focus mid-semester, resulting in compressed 
development timeline for final deliverable.


MEETING SUMMARY INDEX
================================================================================

Meeting 1 (Sprint 1) - Early Development Phase
  Date: [Week 3-4]
  Time: 8:15pm - 10:00pm
  Focus: Project scope definition, requirements gathering, initial design
  
Meeting 2 (Sprint 2) - Core Development  
  Date: [Week 5-6]
  Time: 8:00pm - 10:00pm
  Focus: Data storage implementation, algorithm design, estimation logic

Meeting 3 (Sprint 3) - Integration & Testing
  Date: [Week 6-7]
  Time: 5:00pm - 7:20pm
  Focus: Algorithm refinement, testing, integration work

Meeting 4 (Final Sprint) - Polish & Delivery
  Date: [Week 8]
  Time: 5:00pm - 7:20pm
  Focus: Final touches, documentation, video recording, website creation


================================================================================
          MEETING 1: PROJECT INITIATION & REQUIREMENTS PHASE
================================================================================

Date: [Early in semester - Week 3-4]
Time Started: 8:15pm
Time Ended: 10:00pm
Duration: 1 hour 45 minutes

--------------------------------------------------------------------------------
AARON DELAROSA
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 3 hours

What Has Been Done:
- Contributed to defining project scope and core features

What Is Planned Until Next Meeting:
- Assist with system architecture design

Blockers/Hurdles:
- Time constraints as we switched our project type mid-semester

--------------------------------------------------------------------------------
FAISAL ALHAZZAA
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 2 hours

What Has Been Done:
- Began working on identifying user inputs such as assignment deadlines,
  workload priority, and available study time

What Is Planned Until Next Meeting:
- Help design basic workflow diagrams for how schedules are generated

Blockers/Hurdles:
- We switched projects so we are a few weeks behind in creating our project

--------------------------------------------------------------------------------
ASHLEY PAUL
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 2 hours

What Has Been Done:
- Contributed to the outline of Project and Mapped User Stories

What Is Planned Until Next Meeting:
- Begin documenting functional requirements and system flow

Blockers/Hurdles:
- Technical limits, and only a rough idea of how the project will work

MEETING 1 SUMMARY:
Total Team Hours: 7 hours
Key Achievements: Project scope defined, user stories mapped, requirements begun
Main Blocker: Project pivot created time pressure


================================================================================
        MEETING 2: DATA STRUCTURE & ALGORITHM DESIGN PHASE
================================================================================

Date: [Week 5-6]
Time Started: 8:00pm
Time Ended: 10:00pm
Duration: 2 hours

--------------------------------------------------------------------------------
AARON DELAROSA
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 3 hours

What Has Been Done:
- Designed and structured the CSV data storage for courses, assignments,
  and availability

What Is Planned Until Next Meeting:
- Assist with connecting stored course data to the dropdown UI component

Blockers/Hurdles:
- Time constraints

--------------------------------------------------------------------------------
FAISAL ALHAZZAA
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 2 hours

What Has Been Done:
- Designed the logic for estimating assignment completion time based on
  description keywords

What Is Planned Until Next Meeting:
- Begin testing estimation accuracy using sample assignments

Blockers/Hurdles:
- Time constraints

--------------------------------------------------------------------------------
ASHLEY PAUL
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 2 hours

What Has Been Done:
- Drafted the scheduling algorithm to distribute workload evenly based on
  due dates and availability

What Is Planned Until Next Meeting:
- Begin testing workload balancing across multiple assignments

Blockers/Hurdles:
- Time constraints

MEETING 2 SUMMARY:
Total Team Hours: 7 hours
Key Achievements: CSV storage designed, estimation logic created, scheduler 
                  algorithm drafted
Main Blocker: Time pressure (consistent across team)


================================================================================
          MEETING 3: TESTING & ALGORITHM REFINEMENT PHASE
================================================================================

Date: [Week 6-7]
Time Started: 5:00pm
Time Ended: 7:20pm
Duration: 2 hours 20 minutes

--------------------------------------------------------------------------------
AARON DELAROSA
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 12 hours

What Has Been Done:
- Adding final touches for a more professional project

What Is Planned Until Next Meeting:
- Continue to add finalized touches as well as record the youtube video
  and create the website

Blockers/Hurdles:
- None at this time

--------------------------------------------------------------------------------
FAISAL ALHAZZAA
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 2 hours

What Has Been Done:
- Designed the logic for estimating assignment completion time based on
  description keywords (continued refinement)

What Is Planned Until Next Meeting:
- Begin testing estimation accuracy using sample assignments

Blockers/Hurdles:
- Time constraints

--------------------------------------------------------------------------------
ASHLEY PAUL
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 2 hours

What Has Been Done:
- Drafted the scheduling algorithm to distribute workload evenly based on
  due dates and availability (refinement phase)

What Is Planned Until Next Meeting:
- Begin testing workload balancing across multiple assignments

Blockers/Hurdles:
- Time constraints

MEETING 3 SUMMARY:
Total Team Hours: 16 hours
Key Achievements: Major progress by Aaron (12 hours), algorithm refinements,
                  preparation for deliverables
Main Blocker: Time (for Faisal & Ashley); Aaron has cleared blockers


================================================================================
            MEETING 4: FINAL DELIVERABLES & POLISH PHASE
================================================================================

Date: [Week 8 - Final week]
Time Started: 5:00pm
Time Ended: 7:20pm
Duration: 2 hours 20 minutes

--------------------------------------------------------------------------------
AARON DELAROSA
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 12 hours

What Has Been Done:
- Adding final touches for a more professional project

What Is Planned Until Next Meeting:
- Continue to add finalized touches as well as record the youtube video
  and create the website

Blockers/Hurdles:
- None at this time

--------------------------------------------------------------------------------
FAISAL ALHAZZAA
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 10 hours

What Has Been Done:
- Designed the logic for estimating assignment completion time based on
  description keywords (finalization)

What Is Planned Until Next Meeting:
- Begin testing estimation accuracy using sample assignments

Blockers/Hurdles:
- Time constraints

--------------------------------------------------------------------------------
ASHLEY PAUL
--------------------------------------------------------------------------------
Hours Worked Since Last Meeting: 6 hours

What Has Been Done:
- Drafted the scheduling algorithm to distribute workload evenly based on
  due dates and availability (final version)

What Is Planned Until Next Meeting:
- Continue refining the schedule algorithm, begin testing its functionality,
  and start working on the project poster

Blockers/Hurdles:
- None at this time

MEETING 4 SUMMARY:
Total Team Hours: 28 hours
Key Achievements: Heavy development sprint (Aaron 12h, Faisal 10h, Ashley 6h),
                  documentation, video production, website creation
Main Blocker: Time (Faisal only); team pushing for final delivery


================================================================================
                        OVERALL PROJECT STATISTICS
================================================================================

TOTAL DOCUMENTED HOURS BY MEMBER:
- Aaron Delarosa:    30 hours (3 + 3 + 12 + 12)
- Faisal Alhazzaa:   16 hours (2 + 2 + 2 + 10)
- Ashley Paul:       12 hours (2 + 2 + 2 + 6)
- TEAM TOTAL:        58 documented hours

Note: These are hours reported in scrum meetings only. Actual development time
likely higher due to individual work between meetings.

MEETING STATISTICS:
- Total Meetings: 4
- Average Duration: 2 hours
- Total Meeting Time: ~8 hours
- Average Hours Worked Between Meetings: 14.5 hours (team combined)

WORK DISTRIBUTION:
- Aaron Delarosa: 52% of documented hours (primary developer role)
- Faisal Alhazzaa: 28% of documented hours (estimation logic focus)
- Ashley Paul: 20% of documented hours (scheduler algorithm focus)

BLOCKERS ANALYSIS:
- Most Common: Time constraints (mentioned 8 times)
- Project-Specific: Mid-semester project pivot
- Resolution: Team overcame blockers by final sprint (2 members clear)


================================================================================
                          TEAM COLLABORATION NOTES
================================================================================

ROLE SPECIALIZATION OBSERVED:
Based on scrum reports, the team naturally divided responsibilities:

Aaron Delarosa:
- Data storage architecture (CSV design)
- UI component integration
- Project polish and professional touches
- Video production and website creation
- Highest individual hour contribution

Faisal Alhazzaa:
- AI estimation logic design
- Keyword-based time estimation algorithm
- Testing estimation accuracy
- Consistent 2-10 hour sprints

Ashley Paul:
- Core scheduling algorithm development
- Workload distribution logic
- Algorithm testing and balancing
- Project poster creation
- Documentation (requirements, system flow)

COLLABORATION PATTERNS:
- Meeting 1: Parallel work on separate components (scoping phase)
- Meeting 2: Individual specialization (each owns a module)
- Meeting 3: Integration beginning (Aaron connecting components)
- Meeting 4: Heavy push for completion (all members contributing)

DEPENDENCIES NOTED:
- Aaron's UI work depends on Faisal & Ashley's algorithms
- Testing phase requires all components functional
- Final deliverables (video, website) coordinated by Aaron


================================================================================
                            SPRINT RETROSPECTIVE
================================================================================

WHAT WENT WELL:
- Clear role specialization - each member owned specific components
- Consistent meeting schedule (5pm or 8pm start times)
- Team overcame mid-semester project pivot
- Strong final push (28 hours in final sprint)
- All blockers resolved by final meeting

CHALLENGES FACED:
- Project type switch mid-semester created time pressure
- Recurring time constraints throughout development
- Compressed timeline due to late start
- Technical uncertainties in early phases

LESSONS LEARNED:
- Early project definition critical (pivot costly)
- Regular scrums help identify blockers quickly
- Specialization effective for small teams
- Time constraints require prioritization

FUTURE IMPROVEMENTS:
- More granular daily standups (currently weekly meetings)
- Earlier integration testing
- More detailed task breakdown in planning phase
- Better time estimation for new technologies


================================================================================
                              DELIVERABLES STATUS
================================================================================

PLANNED DELIVERABLES (from Meeting 4):
✓ Core application functionality
✓ Professional project polish
✓ YouTube demonstration video
✓ Project website
✓ Project poster
✓ Documentation (requirements, system flow)

TECHNICAL COMPONENTS COMPLETED:
✓ CSV data storage system (Aaron)
✓ AI estimation logic (Faisal)
✓ Scheduling algorithm (Ashley)
✓ UI components and integration (Aaron)
✓ Testing framework


================================================================================
                            SUBMISSION NOTES
================================================================================

This compilation represents all documented daily scrum meetings for the
Academic Planner project team (Aaron Delarosa, Faisal Alhazzaa, Ashley Paul)
during Spring 2025 semester.

The team maintained a consistent meeting schedule and successfully delivered
a functional AI-powered academic workload management system despite mid-semester
project changes.

Total documented work: 58 hours across 4 scrum meetings
Project outcome: Complete working application with documentation

Compiled by: Aaron Delarosa
Date: April 27, 2025

================================================================================
                                END OF LOG
================================================================================
